v2 300%
(ECI)'
Here is a MWE that generates these errors:
setupinteraction
[title=TITLE,
subtitle=SUBTITLE,
author=AUTHOR,
keyword={{KEYWORD1, KEYWORD2}, KEYWORD3}]
%% For PDF/A
\setupbackend[
format={pdf/a-1b:2005}, % or pdf/a-1a:2005
profile={default_cmyk.icc,default_rgb.icc,de
subtitle=SUBTITLE,
author=AUTHOR,
keyword={{KEYWORD1, KEYWORD2}, KEYWORD3}]
%% For PDF/A
\setupbackend[
format={pdf/a-1b:2005}, % or pdf/a-1a:2005
profile={default_cmyk.icc,default_rgb.icc,default_gray.icc},
intent=ISO coated v2 300\letterpercent\space (ECI)]
%% Tagged PDF
%% method=auto =
eback:
...ocal/share/texmf-dist/tex/context/base/mkxl/node-mig.lmt:19: in
local 'code'
...ocal/share/texmf-dist/tex/context/base/mkiv/util-lua.lua:96: in
field 'loadedluacode'
...ocal/share/texmf-dist/tex/context/base/mkiv/luat-env.lua:108: in
field 'luafilechu
>
>> On 10/9/2022 8:03 AM, Max Chernoff via ntg-context wrote:
>>> Hi all,
>>>
>>>> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>>>>
>>>> Here's a tiny test document, I disabled PDF compression but it also
&g
>>> doesn't work with the default settings.
>>>
>>> \setupbackend[level=0,compresslevel=0]
>>> \starttext
>>> Just a line of text.
>>> \stoptext
>>>
>>> When I print this "directly" (i.e. sending the raw PDF to the printe
On 10/9/2022 8:03 AM, Max Chernoff via ntg-context wrote:
Hi all,
I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
Here's a tiny test document, I disabled PDF compression but it also
doesn't work with the default settings.
\setupbackend[level=0,compresslevel=0]
\starttext
Just
Hi all,
> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>
> Here's a tiny test document, I disabled PDF compression but it also
> doesn't work with the default settings.
>
> \setupbackend[level=0,compresslevel=0]
> \starttext
> Just a line of text.
>
On 10/3/22 20:57, Leah Neukirchen via ntg-context wrote:
>> [...]
>> \setupbackend[level=0,compresslevel=0]
>> \starttext
>> Just a line of text.
>> \stoptext
>> [...]
>
> On Acrobat DC on macOS, there is a visible difference between the two files:
Hi
Hans Hagen via ntg-context writes:
> On 10/3/2022 7:17 PM, Leah Neukirchen via ntg-context wrote:
>> Hi,
>> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>> Here's a tiny test document, I disabled PDF compression but it also
>> doesn't work with the default
On 10/3/2022 7:17 PM, Leah Neukirchen via ntg-context wrote:
Hi,
I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
Here's a tiny test document, I disabled PDF compression but it also
doesn't work with the default settings.
\setupbackend[level=0,compresslevel=0]
\starttext
Just a line
Leah Neukirchen via ntg-context writes:
> Hi,
>
> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>
> Here's a tiny test document, I disabled PDF compression but it also
> doesn't work with the default settings.
>
> \setupbackend[level=0,compresslevel=0]
&g
Hi,
I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
Here's a tiny test document, I disabled PDF compression but it also
doesn't work with the default settings.
\setupbackend[level=0,compresslevel=0]
\starttext
Just a line of text.
\stoptext
When I print this "directly" (i.
on how to resolve this?
As you like challenges ... you can way more narrow it down ...
\setupbackend[export=yes]
\starttext
{
\forgetall
% \forgeteverypar
x\strut\par
}
\stoptext
the problem is that you basically loose *all* par related tagging now so
you need to bring that back,
> >
> > gives the fuzzy paragraph warning. Any hints on how to resolve this?
> As you like challenges ... you can way more narrow it down ...
>
> \setupbackend[export=yes]
>
> \starttext
> {
> \forgetall
>% \forgeteverypar
> x\strut\par
> }
> \
t down to the attached MWE (which does not depend on
the t-vim module at all). Compiling it using
$context --trackers=export\* lines
gives the fuzzy paragraph warning. Any hints on how to resolve this?
As you like challenges ... you can way more narrow it down ...
\setupbackend[export=yes]
\sta
Hi Pablo and Rik
many thanks, much appreciated.
attachment works like a charm to include the source files in the delivered PDF.
Rik pointed me to the longterm archive standard, which is also desirable. PDF/A
is possible with setupbackend\setupbackend[format={pdf/a-3a}]
but needs fixing
Hi Pablo
Many thanks. That is exactly what I need, ie. to deliver the source code
embedded in the PDF.
attachment works like a charm
Rik pointed me — additionally — into the direction of being PDF/A compliant.
PDF/A is possible with
setupbackend\setupbackend[format={pdf/a-3a}]
but needs
ot;, though.
— html-test.tex —
\definefontfamily [mainface][math][stix]
\setupbodyfont[mainface,10pt]
\setupinteraction[state=start, click=yes, focus=standard, color=darkblue]
\setupbackend[export=yes] % Exporting HTML/XML
\defineregister [index]
\setupregister [index] [indi
on PDF/A
<https://wiki.contextgarden.net/PDF/A>:
---
\setupinteraction[title=MyTitle,state=start]
\setupinteractionscreen[option={title}]
\setupbackend[
format={pdf/a-1a:2005},
profile={default_cmyk.icc,default_rgb.icc,default_gray.icc},
intent=ISO coated v2 300\letterpercent\spac
PDF/A>:
---
\setupinteraction[title=MyTitle,state=start]
\setupinteractionscreen[option={title}]
\setupbackend[
format={pdf/a-1a:2005},
profile={default_cmyk.icc,default_rgb.icc,default_gray.icc},
intent=ISO coated v2 300\letterpercent\space (ECI)]
%% Tagged PDF
%% method=auto ==> def
On 5/22/21 12:25 PM, Hans Hagen wrote:
> On 5/22/2021 11:28 AM, Pablo Rodriguez wrote:
>> [...]
>> Using SumatraPDF-3.1.2 and current latest (from 2021.05.21 15:07),
>> spacing is only right when I disable font expansion.
>>
>> Would it be possible that spacing be the same with and without font
>>
On 5/22/2021 11:28 AM, Pablo Rodriguez wrote:
Hi Hans,
I have the following sample:
\definefontfeature
[default]
[default]
[expansion=quality]
\setupalign
[hz]
\setuppapersize[A6]
\setupbodyfont[pagella]
\setupbackend [space=yes]
\starttext
\input
Hi Hans,
I have the following sample:
\definefontfeature
[default]
[default]
[expansion=quality]
\setupalign
[hz]
\setuppapersize[A6]
\setupbodyfont[pagella]
\setupbackend [space=yes]
\starttext
\input zapf
\stoptext
Using SumatraPDF-3.1.2 and current latest
On 5/10/21 9:36 AM, Hans Hagen wrote:
> [...]
> but at the cost of runtime you can try \setupbackend [space=yes]
It works perfectly fine, but not with font expansion:
\definefontfeature
[default]
[default]
[expansion=quality]
\setupalign
[hz]
\setuppapers
,
and think that a widely--praised program,
called up on the screen, will make every-
thing automatic from now on.
but at the cost of runtime you can try \setupbackend [space=yes]
Hans
-
Hans Hagen
On 4/26/2021 7:04 PM, Pablo Rodriguez wrote:
Dear list,
I have the following sample:
\setupbackend
[format=PDF/A-3a,
intent=sRGB IEC61966-2.1,
profile={sRGB, default_gray.icc},
level=0]
\setuptagging[state=start]
\setupcolors[cmyk=no, pagecolormodel=auto
Dear list,
I have the following sample:
\setupbackend
[format=PDF/A-3a,
intent=sRGB IEC61966-2.1,
profile={sRGB, default_gray.icc},
level=0]
\setuptagging[state=start]
\setupcolors[cmyk=no, pagecolormodel=auto]
\definefontfamily[mainface][rm][TeX Gyre Heros
On 2/28/2021 11:42 AM, a badin wrote:
% \setupbackend[export=example.xml,css=example.css]
\usebtxdataset[default][ref.bib]
\starttext
\cite[Arrow][Arrow]
\placelistofpublications
\stoptext
my ref.bib file:
@ARTICLE{Arrow,
author = {Andrej Arrow},
title = {The Font Name Mess},
journal
ear gardeners,
>
> I'm new to ConTeXt and would like to share a possible bug with you.
>
> If I have the \setupbackend[export=example.xml,css=example.css] entry in
> my .tex file, then my bibliography renders in a strange way (text copied
> from pdf): 1 bfldcategoryarticle:
Dear gardeners,
I'm new to ConTeXt and would like to share a possible bug with you.
If I have the \setupbackend[export=example.xml,css=example.css] entry in my
.tex file, then my bibliography renders in a strange way (text copied from
pdf): 1 bfldcategoryarticle: [author: Andrej Arrow] [journal
tree:
test.tex
styles/mystyle.css
where test.tex is:
```
\setupbackend[export=yes]
\setupexport[cssfile=styles/mystyle.css]
\starttext
\startparagraph
This is a test
\stopparagraph
\stoptext
```
and
styles/mystyle.tex is (the content doesn't matter, listing it for completeness
uckerei
%% nachfragen.
\setupbackend[
%format=PDF/X-1a:2001,
%format=PDF/X-1a:2003,
%format=PDF/X-3:2002,
format=PDF/X-3:2003,
%format=PDF/X-4,
%format=PDF/X-4p,
intent={ISO Coated v2 300\letterpercent\space (ECI)},
]
\stopmode
%% FOGRA 39 Coated
%% Bestimmung der CMYK-We
enalty
\endcsname \lastnamedcs \else \page_otr_command_routine
\fi
{\inotrtrue \the \everybeforeoutput \page_otr_triggered_output_routine
\relax \the \everyafteroutput }
...
\stopproduct
Are there changes with modes or setupbackend in lmtx?
My configuration is:
\setupbackend[
format=P
[bidi=global,method=unicode]
\setupbackend[export=yes]
\setupstructure[state=start,method=auto]
\starttext
\starttabulate[|p|p|]
\NC Text
\NC Translation
\NC\NR
\NC\setupalign[r2l]\input ward
\NC\input ward
\NC\NR
\stoptabulate
\stoptext
==
Why is that?
The export can lead
]
\starttext
\starttabulate[|p|p|]
\NC Text
\NC Translation
\NC\NR
\NC\setupalign[r2l]\input ward
\NC\input ward
\NC\NR
\stoptabulate
\stoptext
==
But, this here fails:
\setupalign[verytolerant,stretch]
\setupdirections[bidi=global,method=unicode]
\setupbackend[export
\NC Translation
\NC\NR
\NC\setupalign[r2l]\input ward
\NC\input ward
\NC\NR
\stoptabulate
\stoptext
==
But, this here fails:
\setupalign[verytolerant,stretch]
\setupdirections[bidi=global,method=unicode]
\setupbackend[export=yes]
\setupstructure[state=start,method=auto
ward
\NC\input ward
\NC\NR
\stoptabulate
\stoptext
==
But, this here fails:
\setupalign[verytolerant,stretch]
\setupdirections[bidi=global,method=unicode]
\setupbackend[export=yes]
\setupstructure[state=start,method=auto]
\starttext
\starttabulate[|p|p|]
\NC Text
\NC
\stoptext
==
But, this here fails:
\setupalign[verytolerant,stretch]
\setupdirections[bidi=global,method=unicode]
\setupbackend[export=yes]
\setupstructure[state=start,method=auto]
\starttext
\starttabulate[|p|p|]
\NC Text
\NC Translation
\NC\NR
\NC\setupalign[r2l]\input
, minor) work in LMTX?
It does not give an error, but it doesn't change the minor version
either.
1. A better solution for this is to add a key to \setupbackend.
2. It doesn't work because when you set the version it's too late
because ConTeXt already wrote the PDF header (the relevant code
; they state "Ensure that you are using a CMYK workflow and export to
> PDF/X-1a:2001" . I can set the pdf format using \setupbackend but I'm
> unsure as to what to do about CMYK workflow. The book has no colour pages
> so I'm not sure if I really need to worry about CMYK workflow.
> Am 23.06.2020 um 22:28 schrieb Keith McKay :
>
> Colleagues
>
> I'm getting ready to send a book to the printers and in their blurb they
> state "Ensure that you are using a CMYK workflow and export to PDF/X-1a:2001"
> . I can set the pdf format usi
Colleagues
I'm getting ready to send a book to the printers and in their blurb
they state "/Ensure that you are using a CMYK workflow and export to
PDF/X-1a:2001" . /I can set the pdf format using \setupbackend but I'm
unsure as to what to do about CMYK workflow. The book has
{xmpfile}}\ifempty
\p_file \else
\clf_setxmpf...
\setup_backend ...end [#1]\the \everysetupbackend
l.11 ...ISO coated v2 300\letterpercent\space (ECI)]
mtx-context | fatal error: return code: 1
Removing either of the \setupbackend
{xmpfile}}\ifempty
\p_file \else
\clf_setxmpf...
\setup_backend ...end [#1]\the \everysetupbackend
l.11 ...ISO coated v2 300\letterpercent\space (ECI)]
mtx-context | fatal error: return code: 1
Removing either of the \setupbackend
\p_file \else
\clf_setxmpf...
\setup_backend ...end [#1]\the \everysetupbackend
l.11 ...ISO coated v2 300\letterpercent\space (ECI)]
mtx-context | fatal error: return code: 1
Removing either of the \setupbackend instructions still results in the
same error
][name=whatever]
should work (there are some such examples in the texmf tree), but it does
not.
epub-mkiv.pdf states that I need `\setupexport[properties=yes]`, but that
doesn't work either:
```
\setupbackend[export=xml]
\setupexport [properties=my]
\setelementbackendtag[mycommand
is
...
(or some variant of that). I thought that
\startelement[mycommand][name=whatever]
should work (there are some such examples in the texmf tree), but it does not.
```
\setelementbackendtag[mycommand]
\setelementnature[mycommand][mixed]
\setupbackend[export=xml, level=0]
\starttext
On 5/18/2020 9:09 AM, Aditya Mahajan wrote:
Hi,
What is needed to enable export of user defined macros? Consider the
following example:
```
\def\startmycommand{\dostarttagged{mycommand}\empty}
\def\stopmycommand {\dostoptagged}
\setupbackend[export=xml, level=0]
\starttext
\startsection
Hi,
What is needed to enable export of user defined macros? Consider the following
example:
```
\def\startmycommand{\dostarttagged{mycommand}\empty}
\def\stopmycommand {\dostoptagged}
\setupbackend[export=xml, level=0]
\starttext
\startsection[title={Sample document}]
\startparagraph
[location=middle, marking=on]
\setupinteraction
[title={TestDoc},
author={Anon}]
\setupbackend
[format=PDF/X-1a:2003,
intent={ISO Coated v2 300\letterpercent\space (ECI)}]
\setupinteractionscreen[width=max,height=max]
\startluacode
moduledata.mystuff={}
respecify_pdf_boxes = function
iple output for
> publishing
> ane educational purposes. And it looks pretty good too.
>
Thank you very much i will do. You are refering to Thomas Schmitz?
\setupbackend[
export=yes,
xhtml=yes
]
\setupexport[
title={linenumber placement missmatch example in export},
subtitle={},
au
uot; or "flex" (not jet decided" which).
> 2) How can i predefine the white-space css attribute to pre-wrap
> 3) Is there a way to tell context to include the resulting class
> inside
> the *.default.css or *.styles.css or should that be done via the css
> para
3) Is there a way to tell context to include the resulting class inside
the *.default.css or *.styles.css or should that be done via the css
parameter of the \setupbackend macro only?
Best
Xristoph
___
If your questi
Instructions for creating the .epub from the export are contained in the
log file.
On 3/3/2020 15:58, Hans van der Meer wrote:
I followed your advice and added the setup:
You need
\setupbackend[export=yes]
in your document.
This, however, does not result in an .epub file but an export
On Tue, 3 Mar 2020 21:58:16 +0100
Hans van der Meer wrote:
> I followed your advice and added the setup:
>
> > You need
> > \setupbackend[export=yes]
> > in your document.
>
> This, however, does not result in an .epub file but an export directory
> contai
I followed your advice and added the setup:
> You need
> \setupbackend[export=yes]
> in your document.
This, however, does not result in an .epub file but an export directory
containing an html and xhtml file (only partially conformant to the equivalent
pdf).
Can I get t
et without
> that mode.
You need
\setupbackend[export=yes]
in your document. When you put the setup above in a "epub"
mode you create a epub-document only when you enable the mode
which is recommended because it can have side effects for
the normal PDF.
To avoid these side effects make a
On 2/27/2020 3:19 PM, Robin Schwab wrote:
Hi,
I am looking for a LaTeX system that can create accessible PDF so I
tried ConTeXt.
In current ConTeXt it seems to be impossible to specify more than one
\setupbackend[format
Minimal example:
\setupbackend[format={pdf/a-3a,pdf/ua-1,pdf/x-4
Hi,
I am looking for a LaTeX system that can create accessible PDF so I
tried ConTeXt.
In current ConTeXt it seems to be impossible to specify more than one
\setupbackend[format
Minimal example:
\setupbackend[format={pdf/a-3a,pdf/ua-1,pdf/x-4}]
\starttext
\input knuth
\stoptext
I get
>> Colors that you define in TeX or Metapost are a different problem. I
>> *think* they should use the output intent as their profile. But I
>> don’t know if the intent option of \setupcolors and/or \setupbackend
>> really works this way. (My only means to check was Acrobat P
to CMYK with the above cited profile chain?
Or shall I tell the designer: These are the values I need as CMYK, just
do it.
> Colors that you define in TeX or Metapost are a different problem. I
> *think* they should use the output intent as their profile. But I
> don’t know if the intent option
intent as their profile. But I don’t know if the
intent option of \setupcolors and/or \setupbackend really works this way. (My
only means to check was Acrobat Pro 9, and that won’t run on a current macOS
any more.)
Hope that helps a bit and doesn’t confuse you more…
Color management *is* hard
and specialty offset, paper type 4,
uncoated white paper, positive plates, tone value increase curves C
(CMY) and D (K), white backing.
Copy the icc-profile into the same folder as the shipped profiles. Call
"context --make" to make a new format, update the file dat
[state=start]
\setupinteraction [state=start]
%setupbackend[format={pdf/a-3u},
\setupbackend[format={pdf/a-3a},
level=0,
profile={default_gray.icc},
intent={ISO coated v2 300\lett
Am 12.02.2020 um 09:41 schrieb juh:
> Hi all,
>
> again I have a question concerning color profiles.
>
> I have this to load the ISO Coated v2 300% profile.
>
> \setupbackend[
>format=PDF/X-3:2003,
>intent={ISO Coated v2 300\letterpercent\space (ECI)},
>]
Hi all,
again I have a question concerning color profiles.
I have this to load the ISO Coated v2 300% profile.
\setupbackend[
format=PDF/X-3:2003,
intent={ISO Coated v2 300\letterpercent\space (ECI)},
]
\setupcolors[cmyk=yes,rgb=no,]
But is this profile part of the new lmtx version
pdf-1.5.18 and the following
>> sample:
>>
>> \setuptagging[state=start]
>>
>> \setupbodyfont[30pt]
>>
>> \setupbackend
>> [format=PDF/A-3a,
>> intent=sRGB IEC61966-2.1,
>> profile={sRGB.icc,default_g
fail validation with the same issues.
Hi Rik,
it has way less issues, at least using verapdf-1.5.18 and the following
sample:
\setuptagging[state=start]
\setupbodyfont[30pt]
\setupbackend
[format=PDF/A-3a,
intent=sRGB IEC61966-2.1,
profile={sRGB.icc
dation with the same issues.
Hi Rik,
it has way less issues, at least using verapdf-1.5.18 and the following
sample:
\setuptagging[state=start]
\setupbodyfont[30pt]
\setupbackend
[format=PDF/A-3a,
intent=sRGB IEC61966-2.1,
profile={sRGB.icc,defaul
=\endash~,
% midsentence=~\endash,
rightsentence=~\endash]
\define\quotedash{\emdash\endash}
%\setupbackend[export=yes]
\starttext
\startsection[title=Introduction]
Any of you able to help me get my quotation dashes into line when
automatically
inserted by the semantic commands? I'm sure
On 1/10/2020 10:59, Rik Kabel wrote:
Here ya go, about as minimal as I can imagine:
\setupbackend [export=yes]
\setupexport []
\starttext
!
\stoptext
and in the resulting export styles directory, I get:
g:\yoiks-export\styles>grep "namespace\|weight.*ital
ly assigns italic to font-weight when of course it is
a font-style as far as css is concerned. This can be seen in file
export-example.css in the distribution.
can you make a mwe ...
Here ya go, about as minimal as I can imagine:
\setupbackend [export=yes]
\setupexport []
=~\endash,
rightsentence=~\endash]
\define\quotedash{\emdash\endash}
%\setupbackend[export=yes]
\starttext
\startsection[title=Introduction]
Any of you able to help me get my quotation dashes into line when
automatically
inserted by the semantic commands? I'm sure a number of you look
>> try to make an PDF/X.
>>
>> I hope that is solvable...
>>
>> \setupbackend[format=PDF/X-1a:2001]
>>
>> \starttext
>> \externalfigure[kinder/esel_kl]
>> \stoptext
>>
>>
>> Best, Hraban
>>
>> __
cy.
>
>
> Peter
>
>
confirmed, this is ok.
\setupbackend[format=PDF/X-4p]
\starttext
\externalfigure[esel_kl.png]
\stoptext
>
--
luigi
___
If your question is of interest to others as well, please add
Henning Hraban Ramm writes:
> I think this is the same problem that I had in Bassenge:
> The transparent part of PNGs like the attached one becomes black if I try to
> make an PDF/X.
>
> I hope that is solvable...
>
> \setupbackend[format=PDF/X-1a:2001]
AFAIK PDF/X-1a:
ink this is the same problem that I had in Bassenge:
> The transparent part of PNGs like the attached one becomes black if I
> try to make an PDF/X.
>
> I hope that is solvable...
>
> \setupbackend[format=PDF/X-1a:2001]
>
> \starttext
> \externalfigure[kinder/esel_kl]
I think this is the same problem that I had in Bassenge:
The transparent part of PNGs like the attached one becomes black if I try to
make an PDF/X.
I hope that is solvable...
\setupbackend[format=PDF/X-1a:2001]
\starttext
\externalfigure[kinder/esel_kl]
\stoptext
Best, Hraban
ping it only to the K channel.
I’d regard that a misconfiguration on their side.
Maybe it helps to define the output intent:
https://wiki.contextgarden.net/Command/setupbackend
https://wiki.contextgarden.net/PDFX
>> If you need more control you can create your own marks and add them as
>> backgr
achment.
>
> \setuplanguage [en]
> \setuptagging [state=start]
> \setupinteraction [state=start]
> \setupbackend [format={pdf/a-3a},profile={default_gray.icc},
> intent={ISO coated v2 300\letterpercent\space
> (ECI)}]
>
Hello list,
The following document fails PDF/A-3a validation. It passes without the
attachment.
\setuplanguage [en]
\setuptagging [state=start]
\setupinteraction [state=start]
\setupbackend [format={pdf/a-3a},profile={default_gray.icc
on of \vI, then
we get every elements (but of course we get unnecessary "a" also).
- bSample
\setupbackend[export=yes]
\definemathmatrix[vmatrix][matrix:bars]
[simplecommand=Vmatrix]
\define[1]\vsym{\text{\math{\bi #1}}}
\define\vI{\vsym{i}}
% \define\vi{\vsy
rbprofilnichtgefunden}
>% This will be printed in log if context does not find the profile for
>% some reason
>
>\definecolor [hs-logoblau] [c=1.000, m=0.735, y=0.279, k=0.160]
>
>\definecolor [hs-dunkelblau] [c=0.844, m=0.544, y=0.070, k=0.000]
>
>\definecolor [hs-hellblau]
-hellblau] [c=0.468, m=0.220, y=0.086, k=0.002]
\definecolor [hs-orange] [c=0.127, m=0.832, y=1.000, k=0.042]
\setupcolors[cmyk=yes,rgb=no,]
\setupbackend[
format=PDF/X-3:2003,
intent={Coated FOGRA39 (ISO 12647-2:2004)},
]
\stopmode
If you call context with --mode=fogra39 you will
On 5/22/2019 10:30 PM, Procházka Lukáš Ing. wrote:
Hello,
suppose having "Main.mkiv":
\setupbackend[export=yes]
\starttext
\startsection[title={Sec},MyPar=MyVal]
\input knuth
\stopsection
\stoptext
Some questions concerning XML export:
1. Normally, with \se
Hello,
suppose having "Main.mkiv":
\setupbackend[export=yes]
\starttext
\startsection[title={Sec},MyPar=MyVal]
\input knuth
\stopsection
\stoptext
Some questions concerning XML export:
1. Normally, with \setupbackend[export=yes], Ctx creates "Main-exp
On 2/6/2019 7:31 PM, Pablo Rodriguez wrote:
On 2/5/19 8:07 AM, Jan U. Hasecke wrote:
Hola Pablo,
Hallo Jan-Ulrich,
I inserted this in the setupbackend command so that ConTeXt stops with
the unknown command \colorprofilenotfound I inserted in the else clause.
But more and more I think
Am 06.02.19 um 19:31 schrieb Pablo Rodriguez:
> On 2/5/19 8:07 AM, Jan U. Hasecke wrote:
>> Hola Pablo,
>
> Hallo Jan-Ulrich,
>
>> I inserted this in the setupbackend command so that ConTeXt stops with
>> the unknown command \colorprofilenotfound I inserted in t
On 2/5/19 8:07 AM, Jan U. Hasecke wrote:
> Hola Pablo,
Hallo Jan-Ulrich,
> I inserted this in the setupbackend command so that ConTeXt stops with
> the unknown command \colorprofilenotfound I inserted in the else clause.
>
> But more and more I think that ConTeXt should fail if i
\doiffileelse{srgb.icc}{fine now}{\red\ss\bfd HUGE MISTAKE}
>
> \doiffileelse{srgb.icca}{fine now}{\red\ss\bfd HUGE MISTAKE}
> \stoptext
>
> The first profile is provided within the ConTeXt Suite, the second one
> is a wrong file name.
>
> Just in case i
Am 03.02.19 um 15:26 schrieb Jan U. Hasecke:
> I get an error when I use.
>
> \setupbackend[
>format=PDF/X-3:2003,
>intent={Coated FOGRA39 (ISO 12647-2:2004)},
>]
>
> backend > profiles > profile specification 'Coated FOGRA39 (ISO
> 12647-
I get an error when I use.
\setupbackend[
format=PDF/X-3:2003,
intent={Coated FOGRA39 (ISO 12647-2:2004)},
]
backend > profiles > profile specification 'Coated FOGRA39 (ISO
12647-2:2004)' loaded from
'/home/juh/context/tex/texmf-context/colors/icc/context/colorprofil
Hi all,
I downloaded some color profiles and stored them in:
/context/tex/texmf-context/colors/icc/profiles
But they get overwritten, when I update context.
Can I put color profiles in the working folder of my project. And how do
I access them with setupbackend?
TIA
juh
--
Software
A happy new year to everyone!
I’m trying to generate PDF/A compliant files and have a Problem with chemical
formulas in text.
The following does not work:
\setupinteraction
[title=TITLE,
subtitle=SUBTITLE,
author=AUTHOR,
keyword={{KEYWORD1, KEYWORD2}, KEYWORD3}]
%% For PDF/A
\setupbackend
through tagged as a
paragraph and I am unable to add any alternative text. This is the code I am
using:
\setupbackend
[format=PDF/X-1a:2001,
export=yes]
\externalfigure[district.pdf][height=10cm]
Does anyone have any idea how I could fix this?
Thanks!
Claire
eyword={{KEYWORD1, KEYWORD2}, KEYWORD3}]
%% For PDF/A
\setupbackend[
%format={pdf/a-1b:2005}, % OK
%format={pdf/a-1a:2005}, % OK
%format={pdf/a-2a}, % OK
format={pdf/a-3a}, % OK
profile={srgb.icc,default_gray.icc},
intent=ISO coated v2 300\letterpercent\space (ECI)]
%% Tagged PDF
%% m
idate.aspx
>>
>>
>>
> Thank you for the report, I will check asap.
>
>
these look ok now
\nopdfcompression
\setupinteraction
[title=TITLE,
subtitle=SUBTITLE,
author=AUTHOR,
keyword={{KEYWORD1, KEYWORD2}, KEYWORD3}]
%% For PDF/A
\setupbackend[
%format={pdf/a-1b:200
space already!
>>
>> Objects with embedded color profiles (e.g. a PDF bitmap graphic with icc
>> profile) will use those. Objects without a profile will use the
>> corresponding "default" color space profiles. These default color space
>> profiles can be de
c
> profile) will use those. Objects without a profile will use the
> corresponding "default" color space profiles. These default color space
> profiles can be defined via "profile" in \setupbackend.
> This way every color in the PDF is defined properly.
This would cla
se default color space
profiles can be defined via "profile" in \setupbackend.
This way every color in the PDF is defined properly.
(2)
I think so. Can't test, because my Windows 10 is beyond repair after
three "upgrades" and Acrobat is not working properly anymore.
(3)
Judg
1 - 100 of 429 matches
Mail list logo
